

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

<html>
<head>
<script type="text/javascript" src="helpman_topicinit.js"></script>

<title>Setup for Build and Run [Enterprise Architect User Guide]</title>

<meta name="keywords" content="Enterprise Architect, Sparx Systems, UML, Build And Run,Build And Run Source Code Configuration,Code Engineering,Code Engineering Build And Run, Source Code Configuration,Source Code,Source Code Configuration, Build And Run">
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
<meta http-equiv="Content-Style-Type" content="text/css" />

<link type="text/css" href="default.css" rel="stylesheet" />
<style type="text/css">
  A, A:Visited
  {
    color: #00F;
  }

  A:Active, A:Hover
  {
    color: #F00;
  }

  OL
  {
    margin: 5px 0 5px 48px;
  }

  UL
  {
    margin-bottom: 3px;
    margin-top: 0;
  }

  #nsr
  {
    background-color: #D4DFFF;
  }

  #nsr A
  {
    text-decoration: none;
  }

  #mainbody
  {
    padding: 8px;
  }

  .p_BodyText
  {
    padding: 5px 0;
  }
</style>



<style type="text/css" media="screen">
  BODY
  {
    background-color: #FFFFFF;
  }

  #nsr
  {
    padding: 6px 6px 0 6px;
    border-bottom: none;
    vertical-align: top;
    z-index: 2;
    visibility: visible;
    left: 0;
    top: 0;
    position: absolute;
  }

  #mainbody
  {
    left: 0;
    top: 0;
    margin: 0;
    position: absolute;
    padding: 10px;
    overflow: auto;
    height: 100%;
    z-index: 1;
    background-repeat: no-repeat;
    background-position: bottom right;
    background-attachment: fixed;
  }
</style>

<style type="text/css" media="print">
  #nsr
  {
    visibility: none;
  }

  #mainbody
  {
    overflow: visible;
  }
</style>
<script type="text/javascript" language="JavaScript" src="nonscroll.js"></script>

</head>
<body scroll="no">

<div id="page">



        <div id="content">
          <div id="content-inner">
          



  
          <div id="nsr">
            <table border="0" cellspacing="0" cellpadding="4" width="100%">
              <tr valign="top">
                <td align="left">
  


                  <p class="p_Heading1"><span class="f_Heading1">Setup for Build and Run</span></p>



  
                </td>
                <td align="right">
                  <a href="introduction.htm" onmouseover="document.images.main.src='button_main_h.gif'" onmouseout="document.images.main.src='button_main.gif'">
                    <img name="main" src="button_main.gif" border=0 alt="Return to Introduction">
                  </a>&nbsp;
    
                  <a href="buildandrun.htm" onmouseover="document.images.prev.src='button_prev_h.gif'" onmouseout="document.images.prev.src='button_prev.gif'">
                    <img name=prev src="button_prev.gif" border=0 alt="Previous page" />
                  </a>&nbsp;
    
    
    
                  <a href="managingcomplilescripts.htm" onmouseover="document.images.next.src='button_next_h.gif'" onmouseout="document.images.next.src='button_next.gif'">
                    <img name=next src="button_next.gif" border=0 alt="Next page" />
                  </a>
    
    
                </td>
              </tr>
            </table>
          </div>
          <div id="mainbody">
  


                <p class="p_TextIndentedL1"><img src="setup_for_build_and_run.png" width="226" height="100" border="0" alt="setup_for_build_and_run"></p>
<p class="p_BodyText"><span class="f_BodyText">In Enterprise Architect, </span><span class="f_BodyText">any package within the UML Model</span><span class="f_BodyText"> can be configured to act as the 'root' of a source code project. By setting compilation scripts, xUnit commands, debuggers and other configuration settings for a package, all contained source code and elements can be built, tested or debugged according to the currently active configuration. Each package can have multiple scripts, but only one is active at any one time. The </span><span class="f_UIControl">Package Build Scripts</span><span class="f_BodyText"> dialog enables you to create and manage those scripts.</span></p>
<p class="p_BodyText"><span class="f_BodyText">To access the</span><span class="f_UIControl"> Package Build Scripts</span><span class="f_BodyText"> dialog, either:</span></p>
<ul style="text-indent: 0px; margin-left: 30px; list-style-position: outside;">
<li><span class="f_Bulletlist1">Press</span><span class="f_MenuKeyField"> [Shift]+[F12]</span></li>
<li><span class="f_Bulletlist1">On the </span><span class="f_UIControl"><a href="the_debug_toolbar.htm">Debug Toolbar</a></span><span class="f_Bulletlist1">, click on the drop-down arrow on the</span><span class="f_MenuKeyField">Scripts</span><span class="f_Bulletlist1"> icon (the first icon on the left) and select the </span><span class="f_MenuKeyField">Package Build Scripts</span><span class="f_Bulletlist1"> option</span></li>
<li><span class="f_Bulletlist1">Select the </span><span class="f_MenuKeyField">Project | Build and Run | Package Build Scripts</span><span class="f_Bulletlist1"> menu option, or</span></li>
<li><span class="f_Bulletlist1">Right-click on a package in the </span><span class="f_UIControl">Project Browser</span><span class="f_Bulletlist1">, and select the </span><span class="f_MenuKeyField">Build and Run | Package Build Scripts</span><span class="f_Bulletlist1"> menu option.</span></li>
</ul>
<p class="p_TextIndentedL2"><img src="packagebuildscripts.png" width="600" height="413" border="0" alt="PackageBuildScripts"></p>
<p class="p_BodyText"><span class="f_BodyText">The </span><span class="f_UIControl">Package Build Scripts</span><span class="f_BodyText"> dialog shows which script is active for the current package, and whether or not the script contains Build, Test and Run components. The current package is as selected in the </span><span class="f_UIControl">Project Browser</span><span class="f_BodyText">; if a different package is selected, different scripts are available and different breakpoints are applied.</span></p>
<p class="p_BodyText"><span class="f_BodyText">Note that you must close the </span><span class="f_UIControl">Package Build Scripts</span><span class="f_BodyText"> dialog to select a different package in the </span><span class="f_UIControl">Project Browser</span><span class="f_BodyText">. However, if the </span><span class="f_UIControl"><a href="the_debug_window.htm">Debug</a></span><span class="f_BodyText"> window is open (</span><span class="f_MenuKeyField">[Alt]+[8]</span><span class="f_BodyText">) you can see which debugging configuration is available and selected, and which breakpoints are displayed, as you change packages in the </span><span class="f_UIControl">Project Browser</span><span class="f_BodyText">.</span></p>
<ul style="text-indent: 0px; margin-left: 30px; list-style-position: outside;">
<li><span class="f_Bulletlist1">To </span><span class="f_Bulletlist1">create </span><span class="f_Bulletlist1">a new script, click on the </span><span class="f_MenuKeyField">Add</span><span class="f_Bulletlist1"> button; the <a href="build_script_dialog.htm">Build Script dialog</a> displays.</span></li>
<li><span class="f_Bulletlist1">To </span><span class="f_Bulletlist1">modify </span><span class="f_Bulletlist1">an existing script, highlight the script name in the list and click on the </span><span class="f_MenuKeyField">Edit</span><span class="f_Bulletlist1"> button.</span></li>
<li><span class="f_Bulletlist1">To copy a script with a new name, highlight the script name to copy and click on the </span><span class="f_MenuKeyField">Copy</span><span class="f_Bulletlist1"> button; Enterprise Architect prompts you to enter a name for the new copy. Enter the new name in the dialog and click on the </span><span class="f_MenuKeyField">OK</span><span class="f_Bulletlist1"> button. The new copy appears in the list and can be modified as usual.</span></li>
<li><span class="f_Bulletlist1">To delete a script, highlight the script name to delete, click on the </span><span class="f_MenuKeyField">Delete</span><span class="f_Bulletlist1"> button, and click on the </span><span class="f_MenuKeyField">OK</span><span class="f_Bulletlist1"> button.</span></li>
</ul>
<ul style="text-indent: 0px; margin-left: 30px; list-style-position: outside;">
<li><span class="f_Bulletlist1">To export your scripts, click on the </span><span class="f_MenuKeyField">Export</span><span class="f_Bulletlist1"> button to choose the scripts to export for this package.</span></li>
</ul>
<ul style="text-indent: 0px; margin-left: 30px; list-style-position: outside;">
<li><span class="f_Bulletlist1">To </span><span class="f_Bulletlist1">import</span><span class="f_Bulletlist1"> build scripts, click on the </span><span class="f_MenuKeyField">Import</span><span class="f_Bulletlist1"> button to choose a .xml file of the scripts to import.</span></li>
</ul>
<p class="p_BodyText"><span class="f_BodyText">The </span><span class="f_MenuKeyField">Default Language</span><span class="f_BodyText"> field enables you to set the default language for generating source code for all new elements within this package and its descendents.</span></p>
<p class="p_BodyText"><span class="f_BodyText">Select the </span><span class="f_MenuKeyField">Use Live Code Generation</span><span class="f_BodyText"> checkbox to update your source code instantly as you make changes to your model.</span></p>
<p class="p_BodyText"><span class="f_BodyText">Click on the </span><span class="f_MenuKeyField">All Package Scripts</span><span class="f_BodyText"> button to open a new window that displays all scripts in the current project (see the next topic, </span><span class="f_BodyText" style="font-style: italic;"><a href="managingcomplilescripts.htm">Managing Scripts</a></span><span class="f_BodyText">).</span></p>
<p class="p_BodyText"><span class="f_BodyText">Once you have created new scripts or made changes to existing ones, click on the </span><span class="f_MenuKeyField">OK</span><span class="f_BodyText"> button to confirm the changes, otherwise click on the </span><span class="f_MenuKeyField">Cancel</span><span class="f_BodyText"> button to quit the </span><span class="f_UIControl">Package Build Scripts</span><span class="f_BodyText"> dialog without saving any changes.</span></p>




            </div>
          </div>
        </div>



</div>


</body>
</html>
